ISSUE-253: make require-python optionally user path informed #254
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes:
#253
This PR allows for the following sort of exploratory coding style, the PYTHONPATH is managed for the user and reset after execution.
Some alternatives considered:
I attempted, initially, to augment
by adding bindings for Py_SetPath() and Py_GetPath(), but I gave up on that approach. Too many segfaults.
Some difficulties encountered:
I wrote the following testing framework for the new functionality:
It works fine in the REPL, but it 💣 s out with
clojure -A:test
as a result, I believe, of AOT compilation issues. I sunk way more time into the testing than I did into the writing. I'm not sure how to AOT dynamic file creation, so I gave up on that approach, but I'm open to suggestions.